feat: add support for chained jobs #54
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull Request Test Coverage Report for Build 13886627427Details
💛 - Coveralls |
lonnieezell
approved these changes
Mar 17, 2025
|
Thank you @lonnieezell |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds support for chained jobs. Developers can now chain multiple jobs in a sequence. This is particularly useful for breaking down complex workflows into smaller, more manageable tasks that must be executed in a specific order.
Jobs in a chain are stored in the metadata of the previous job. When a job is completed, the queue processor checks if there are any chained jobs in its metadata. If there are, it automatically processes the next job in the chain, preserving any specified priorities and delays.
Checklist: